1z0-062: Oracle Database 12c: Installation and Administration

Which three statements are true about Automatic Workload Repository (AWR)? (Choose three.)

All AWR tables belong to the SYSTEM schema.
The AWR data is stored in memory and in the database.
The snapshots collected by AWR are used by the self-tuning components in the database
AWR computes time model statistics based on time usage for activities, which are displayed in the v$SYS time model and V$SESS_TIME_MODEL views.
AWR contains system wide tracing and logging information.

Correct answer: BCD

You upgraded your database from pre-12c to a multitenant container database (CDB) containing pluggable databases (PDBs).

Examine the query and its output:

Which two tasks must you perform to add users with SYSBACKUP, SYSDG, and SYSKM privilege to the password file? (Choose two.)

Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.
Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.
Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE argument set to No.
Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE arguments set to Yes.
Re-create the password file in the Oracle Database 12c format.

Correct answer: BD

Explanation:

* orapwd / You can create a database password file using the password file creation utility, ORAPWD. The syntax of the ORAPWD command is as follows:orapwd FILE=filename [ENTRIES=numusers] [FORCE={y|n}] [ASM={y|n}] [DBUNIQUENAME=dbname] [FORMAT={12|legacy}] [SYSBACKUP={y|n}] [SYSDG={y|n}] [SYSKM={y|n}] [DELETE={y|n}] [INPUT_FILE=input-fname] force - whether to overwrite existing file (optional), * v$PWFILE_users / 12c: V$PWFILE_USERS lists all users in the password file, and indicates whether the user has been granted the SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, and SYSKM privileges./ 10c: sts users who have been granted SYSDBA and SYSOPER privileges as derived from the password file.ColumnDatatypeDescription USERNAMEVARCHAR2(30)The name of the user that is contained in the password file SYSDBAVARCHAR2(5)If TRUE, the user can connect with SYSDBA privileges SYSOPERVARCHAR2(5)If TRUE, the user can connect with SYSOPER privileges Incorrect:not E: The format of the v$PWFILE_users file is already in 12c format.

* orapwd

/ You can create a database password file using the password file creation utility, ORAPWD.

The syntax of the ORAPWD command is as follows:

orapwd FILE=filename [ENTRIES=numusers] [FORCE={y|n}] [ASM={y|n}]

[DBUNIQUENAME=dbname] [FORMAT={12|legacy}] [SYSBACKUP={y|n}] [SYSDG={y|n}]

[SYSKM={y|n}] [DELETE={y|n}] [INPUT_FILE=input-fname]

force - whether to overwrite existing file (optional),

* v$PWFILE_users

/ 12c: V$PWFILE_USERS lists all users in the password file, and indicates whether the user has been granted the SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, and SYSKM privileges.

/ 10c: sts users who have been granted SYSDBA and SYSOPER privileges as derived from the password file.

ColumnDatatypeDescription

USERNAMEVARCHAR2(30)The name of the user that is contained in the password file

SYSDBAVARCHAR2(5)If TRUE, the user can connect with SYSDBA privileges

SYSOPERVARCHAR2(5)If TRUE, the user can connect with SYSOPER privileges

Incorrect:

not E: The format of the v$PWFILE_users file is already in 12c format.

An application accesses a small lookup table frequently. You notice that the required data blocks are getting aged out of the default buffer cache.

How would you guarantee that the blocks for the table never age out?

Configure the KEEP buffer pool and alter the table with the corresponding storage clause.
Increase the database buffer cache size.
Configure the RECYCLE buffer pool and alter the table with the corresponding storage clause.
Configure Automata Shared Memory Management.
Configure Automatic Memory Management.

Correct answer: A

Explanation:

Schema objects are referenced with varying usage patterns; therefore, their cache behavior may be quite different. Multiple buffer pools enable you to address these differences. You can use a KEEP buffer pool to maintain objects in the buffer cache and a RECYCLE buffer pool to prevent objects from consuming unnecessary space in the cache. When an object is allocated to a cache, all blocks from that object are placed in that cache. Oracle maintains a DEFAULT buffer pool for objects that have not been assigned to one of the buffer pools.

You conned using SQL Plus to the root container of a multitenant container database (CDB) with SYSDBA privilege.

The CDB has several pluggable databases (PDBs) open in the read/write mode.

There are ongoing transactions in both the CDB and PDBs.

What happens alter issuing the SHUTDOWN TRANSACTIONAL statement?

The shutdown proceeds immediately. The shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled hack.
The shutdown proceeds as soon as all transactions in the CDB are either committed or rolled back.
The shutdown proceeds as soon as all transactions in both the CDB and PDBs are either committed or rolled back.
The statement results in an error because there are open PDBs.

Correct answer: B

Explanation:

* SHUTDOWN [ABORT | IMMEDIATE | NORMAL | TRANSACTIONAL [LOCAL]] Shuts down a currently running Oracle Database instance, optionally closing and dismounting a database. If the current database is a pluggable database, only the pluggable database is closed. The consolidated instance continues to run. Shutdown commands that wait for current calls to complete or users to disconnect such as SHUTDOWN NORMAL and SHUTDOWN TRANSACTIONAL have a time limit that the SHUTDOWN command will wait. If all events blocking the shutdown have not occurred within the time limit, the shutdown command cancels with the following message:ORA-01013: user requested cancel of current operation* If logged into a CDB, shutdown closes the CDB instance. To shutdown a CDB or non CDB, you must be connected to the CDB or non CDB instance that you want to close, and then enter SHUTDOWN Database closed. Database dismounted. Oracle instance shut down. To shutdown a PDB, you must log into the PDB to issue the SHUTDOWN command. SHUTDOWN Pluggable Database closed. Note:* Prerequisites for PDB Shutdown When the current container is a pluggable database (PDB), the SHUTDOWN command can only be used if:The current user has SYSDBA, SYSOPER, SYSBACKUP, or SYSDG system privilege. The privilege is either commonly granted or locally granted in the PDB. The current user exercises the privilege using AS SYSDBA, AS SYSOPER, AS SYSBACKUP, or AS SYSDG at connect time. To close a PDB, the PDB must be open.

* SHUTDOWN [ABORT | IMMEDIATE | NORMAL | TRANSACTIONAL [LOCAL]]

Shuts down a currently running Oracle Database instance, optionally closing and dismounting a database. If the current database is a pluggable database, only the pluggable database is closed. The consolidated instance continues to run.

Shutdown commands that wait for current calls to complete or users to disconnect such as SHUTDOWN NORMAL and SHUTDOWN TRANSACTIONAL have a time limit that the SHUTDOWN command will wait. If all events blocking the shutdown have not occurred within the time limit, the shutdown command cancels with the following message:

ORA-01013: user requested cancel of current operation

* If logged into a CDB, shutdown closes the CDB instance.

To shutdown a CDB or non CDB, you must be connected to the CDB or non CDB instance that you want to close, and then enter

SHUTDOWN

Database closed.

Database dismounted.

Oracle instance shut down.

To shutdown a PDB, you must log into the PDB to issue the SHUTDOWN command.

SHUTDOWN

Pluggable Database closed.

Note:

* Prerequisites for PDB Shutdown

When the current container is a pluggable database (PDB), the SHUTDOWN command can only be used if:

The current user has SYSDBA, SYSOPER, SYSBACKUP, or SYSDG system privilege.

The privilege is either commonly granted or locally granted in the PDB.

The current user exercises the privilege using AS SYSDBA, AS SYSOPER, AS SYSBACKUP, or AS SYSDG at connect time.

To close a PDB, the PDB must be open.

You are planning the creation of a new multitenant container database (CDB) and want to store the ROOT and SEED container data files in separate directories.

You plan to create the database using SQL statements.

Which three techniques can you use to achieve this? (Choose three.)

Use Oracle Managed Files (OMF).
Specify the SEED FILE_NAME_CONVERT clause.
Specify the PDB_FILE_NAME_CONVERT initialization parameter.
Specify the DB_FILE_NAMECONVERT initialization parameter.
Specify all files in the CREATE DATABASE statement without using Oracle managed Files (OMF).

Correct answer: ABC

Explanation:

You must specify the names and locations of the seed's files in one of the following ways:(A) Oracle Managed Files (B) The SEED FILE_NAME_CONVERT Clause (C) The PDB_FILE_NAME_CONVERT Initialization Parameter

You must specify the names and locations of the seed's files in one of the following ways:

(A) Oracle Managed Files
(B) The SEED FILE_NAME_CONVERT Clause
(C) The PDB_FILE_NAME_CONVERT Initialization Parameter

You are about to plug a multi-terabyte non-CDB into an existing multitenant container database (CDB).

The characteristics of the non-CDB are as follows:

Version: Oracle Database 11g Release 2 (11.2.0.2.0) 64-bit
Character set: AL32UTF8
National character set: AL16UTF16
O/S: Oracle Linux 6 64-bit

The characteristics of the CDB are as follows:

Version: Oracle Database 12c Release 1 64-bit
Character Set: AL32UTF8
National character set: AL16UTF16
O/S: Oracle Linux 6 64-bit

Which technique should you use to minimize down time while plugging this non-CDB into the CDB?

Transportable database
Transportable tablespace
Data Pump full export/import
The DBMS_PDB package
RMAN

Correct answer: B

Explanation:

* Overview, example:Log into ncdb12c as sys Get the database in a consistent state by shutting it down cleanly. Open the database in read only mode Run DBMS_PDB.DESCRIBE to create an XML file describing the database. Shut down ncdb12c Connect to target CDB (CDB2) Check whether non-cdb (NCDB12c) can be plugged into CDB(CDB2) Plug-in Non-CDB (NCDB12c) as PDB(NCDB12c) into target CDB(CDB2). Access the PDB and run the noncdb_to_pdb.sql script. Open the new PDB in read/write mode. * You can easily plug an Oracle Database 12c non-CDB into a CDB. Just create a PDB manifest file for the non-CDB, and then use the manifest file to create a cloned PDB in the CDB. * Note that to plug in a non-CDB database into a CDB, the non-CDB database needs to be of version 12c as well. So existing 11g databases will need to be upgraded to 12c before they can be part of a 12c CDB.

* Overview, example:

Log into ncdb12c as sys
Get the database in a consistent state by shutting it down cleanly.
Open the database in read only mode
Run DBMS_PDB.DESCRIBE to create an XML file describing the database.
Shut down ncdb12c
Connect to target CDB (CDB2)
Check whether non-cdb (NCDB12c) can be plugged into CDB(CDB2)
Plug-in Non-CDB (NCDB12c) as PDB(NCDB12c) into target CDB(CDB2).
Access the PDB and run the noncdb_to_pdb.sql script.
Open the new PDB in read/write mode.

* You can easily plug an Oracle Database 12c non-CDB into a CDB. Just create a PDB manifest file for the non-CDB, and then use the manifest file to create a cloned PDB in the CDB.

* Note that to plug in a non-CDB database into a CDB, the non-CDB database needs to be of version 12c as well. So existing 11g databases will need to be upgraded to 12c before they can be part of a 12c CDB.

Your database supports an online transaction processing (OLTP) application. The application is undergoing some major schema changes, such as addition of new indexes and materialized views. You want to check the impact of these changes on workload performance.

What should you use to achieve this?

Database replay
SQL Tuning Advisor
SQL Access Advisor
SQL Performance Analyzer
Automatic Workload Repository compare reports

Correct answer: D

Explanation:

You can use the SQL Performance Analyzer to analyze the SQL performance impact of any type of system change. Examples of common system changes include:Database upgrades Configuration changes to the operating system, hardware, or database Database initialization parameter changes Schema changes, such as adding new indexes or materialized views Gathering optimizer statistics SQL tuning actions, such as creating SQL profiles http://docs.oracle.com/cd/B28359_01/server.111/b28318/intro.htm#CNCPT961

You can use the SQL Performance Analyzer to analyze the SQL performance impact of any type of system change. Examples of common system changes include:

Database upgrades
Configuration changes to the operating system, hardware, or database
Database initialization parameter changes
Schema changes, such as adding new indexes or materialized views
Gathering optimizer statistics
SQL tuning actions, such as creating SQL profiles

http://docs.oracle.com/cd/B28359_01/server.111/b28318/intro.htm#CNCPT961

An administrator account is granted the CREATE SESSION and SET CONTAINER system privileges.

A multitenant container database (CDB) instant has the following parameter set:

THREADED_EXECUTION = FALSE

Which four statements are true about this administrator establishing connections to root in a CDB that has been opened in read only mode? (Choose four.)

You can connect as a common user by using the connect statement.
You can connect as a local user by using the connect statement.
You can connect by using easy connect.
You can connect by using OS authentication.
You can connect by using a Net Service name.
You can connect as a local user by using the SET CONTAINER statement.

Correct answer: ACDE

Examine the following query output:

You issue the following command to import tables into the hr schema:

$ > impdp hr/hr directory = dumpdir dumpfile = hr_new.dmp schemas=hr TRANSFORM=DISABLE_ARCHIVE_LOGGING: Y

Which statement is true?

All database operations performed by the impdp command are logged.
Only CREATE INDEX and CREATE TABLE statements generated by the import are logged.
Only CREATE TABLE and ALTER TABLE statements generated by the import are logged.
None of the operations against the master table used by Oracle Data Pump to coordinate its activities are logged.

Correct answer: C

Explanation:

Oracle Data Pump disable redo logging when loading data into tables and when creating indexes. The new TRANSFORM option introduced in data pumps import provides the flexibility to turn off the redo generation for the objects during the course of import. The Master Table is used to track the detailed progress information of a Data Pump job. The Master Table is created in the schema of the current user running the Pump Dump export or import, and it keeps tracks of lots of detailed information.

Oracle Data Pump disable redo logging when loading data into tables and when creating indexes.

The new TRANSFORM option introduced in data pumps import provides the flexibility to turn off the redo generation for the objects during the course of import. The Master Table is used to track the detailed progress information of a Data Pump job.

The Master Table is created in the schema of the current user running the Pump Dump export or import, and it keeps tracks of lots of detailed information.

You notice a performance change in your production Oracle database and you want to know which change has made this performance difference.

You generate the Compare Period Automatic Database Diagnostic Monitor (ADDM) report to further investigation.

Which three findings would you get from the report? (Choose three.)

It detects any configuration change that caused a performance difference in both time periods.
It identifies any workload change that caused a performance difference in both time periods.
It detects the top wait events causing performance degradation.
It shows the resource usage for CPU, memory, and I/O in both time periods.
It shows the difference in the size of memory pools in both time periods.
It gives information about statistics collection in both time periods.

Correct answer: ABD

Explanation:

Keyword: shows the difference.* Full ADDM analysis across two AWR snapshot periods Detects causes, measure effects, then correlates them Causes: workload changes, configuration changesEffects: regressed SQL, reach resource limits (CPU, I/O, memory, interconnect)Makes actionable recommendations along with quantified impact * Identify what changed / Configuration changes, workload changes * Performance degradation of the database occurs when your database was performing optimally in the past, such as 6 months ago, but has gradually degraded to a point where it becomes noticeable to the users. The Automatic Workload Repository (AWR) Compare Periods report enables you to compare database performance between two periods of time. While an AWR report shows AWR data between two snapshots (or two points in time), the AWR Compare Periods report shows the difference (ABE) between two periods (or two AWR reports with a total of four snapshots). Using the AWR Compare Periods report helps you to identify detailed performance attributes and configuration settings that differ between two time periods.

Keyword: shows the difference.

* Full ADDM analysis across two AWR snapshot periods

Detects causes, measure effects, then correlates them

Causes: workload changes, configuration changes

Effects: regressed SQL, reach resource limits (CPU, I/O, memory, interconnect)

Makes actionable recommendations along with quantified impact

* Identify what changed

/ Configuration changes, workload changes

* Performance degradation of the database occurs when your database was performing optimally in the past, such as 6 months ago, but has gradually degraded to a point where it becomes noticeable to the users. The Automatic Workload Repository (AWR) Compare Periods report enables you to compare database performance between two periods of time.

While an AWR report shows AWR data between two snapshots (or two points in time), the AWR Compare Periods report shows the difference (ABE) between two periods (or two AWR reports with a total of four snapshots). Using the AWR Compare Periods report helps you to identify detailed performance attributes and configuration settings that differ between two time periods.